I've used VSCode and edited those 2 files, and made sure the json format was correct and all parameters are linked to the definitions in the bottom part of file.
However due to I've mainly worked with x265.exe instead of libx265, some parameters are missing in libx265 and I cannot gurantee they actually will work (some parameter may get deleted or the definitions needs to be modified if libx265 v3.5 persists not recognizing)
Software is not my profession and I wish I could compile and test the changes myself. Someone needs to compile and check in software to see if the parameters are applied correctly.
Changes also happened in x264 parameters, they have been separated with color profiles (4:2:0 and 4:4:4) thus creates more versions, just 1 version needs to be tested for them.

libx265.json worked prefectly in both value application and encoding (I stopped encoding half way because it's too slow).
libx264.json has some issues, I'll provide images and this change is the fix

Missspelled to 'offest', didn't catch this error previously

…st-scenecut, hist-threshold are currently missing. Deblock formatting was fixed (default CLI was deblock +-int:+-int, but realized it was actually a comma instead of colon)

…st-scenecut, hist-threshold are currently missing. Deblock formatting was fixed (default CLI was deblock +-int:+-int, but realized it was actually a comma instead of colon)

…array (no formatting errors found in VSCode);

Changed default value for --weightp to {value: true} in property array which matches with default true in x265, this doesn't encoding but only reduces confustion

…p Coldwar; disabled mcstf because it still disables multithreading so far (huge performance issue;disabled hist-scenecut due to test reveled stability issue, especially at 12bit)

…--cbqpoffs and --crqpoffs by 2

Tip of this branch is behind official version

…pen-gop toggle failure

…pen-gop toggle failure

…pen-gop toggle failure (2)